Handheld medical interface for intraluminal device and associated devices systems and methods

ABSTRACT

Intraluminal medical devices, systems and methods are provided. In one embodiment, an intraluminal medical system includes a handheld interface device in communication with an intraluminal device to be positioned within a body lumen of a patient. The intraluminal device includes a sensor configured to obtain physiology data associated with the body lumen. The handheld interface device includes a housing sized and shaped for handheld use, a controller core disposed within the housing and configured to control a plurality of sensor types respectively associated with a plurality of intraluminal devices, a computing core disposed within the housing, and a first display integrated in the housing. The controller core is operable to identify the sensor of the intraluminal device, and control the sensor to obtain the physiology data associated with the body lumen. The computing core is operable to process the physiology data using instructions associated with the identified sensor, wherein the computing core is further operable to process physiology data associated with the plurality of sensor types respectively using a plurality of modality specific instructions; and generate a graphical representation based on the physiology data. The first display is operable to display the graphical representation based on the physiology data.

TECHNICAL FIELD

The present disclosure relates generally to handheld medical system and,in particular, intraluminal medical device with a handheld interfacedevice. For example, a handheld medical system can include a handheldinterface device that can identify the type of the sensor of theintraluminal device, process the physiology data obtained by the sensor,and generate a graphical representation of the physiology data.

BACKGROUND

Catheters are widely used as diagnostic tools for assessing a diseasedvessel, such as an artery, within the human body to determine the needfor treatment, to guide the intervention, and/or to assess itseffectiveness. A catheter including one or more sensors is passed intothe vessel and guided to the area of interest. Conventionally, a useroperates the catheter sensor at a large console, such as a desktopcomputer with a tower PC, monitor, keyboard, mouse, and/or other inputdevice. In other instances, a heavy cart-based on system, with a towerPC, monitor, keyboard, mouse, and/or other input device is used.Respective electrical cables are used to connect the console and theintraluminal device to an interface component, which facilitatestransmission of power and/or data signals between the catheter sensorand the console. The presence of numerous, lengthy cables, and large andheavy consoles can inhibit the flexibility that a user has during amedical procedure. This can reduce the efficiency of a medical workflow.Moreover, it typically takes several hours or days to appropriatelyinstall the conventional console-based system.

SUMMARY

Embodiments of the present disclosure provide a handheld medical systemthat includes an intraluminal device coupled to a handheld interfacedevice. The intraluminal device is configured to be inserted into a bodylumen of a patient and a sensor or sensors on the intraluminal device isoperable to obtain physiology data from the body lumen. The handheldinterface device includes a housing that houses a controller core, acomputer core, an analog to digital converter, a signal conditioningcircuit, and a display. The housing is shaped and sized for handhelduse. The handheld interface device receives, conditions, and processesthe physiology data from the intraluminal device, generates a graphicalrepresentation of the physiology data, and displays the graphicalrepresentation on the display.

In one embodiment, an intraluminal medical system includes a handheldinterface device in communication with an intraluminal device configuredto be positioned within a body lumen of a patient. The intraluminaldevice includes a sensor configured to obtain physiology data associatedwith the body lumen. The handheld interface device includes a housingsized and shaped for handheld use, a controller core disposed within thehousing and configured to control a plurality of sensor typesrespectively associated with a plurality of intraluminal devices, acomputing core disposed within the housing, and a first displayintegrated in the housing. The controller core is operable to identifythe sensor of the intraluminal device, and control the sensor to obtainthe physiology data associated with the body lumen. The computing coreis operable to process the physiology data using instructions associatedwith the identified sensor, wherein the computing core is furtheroperable to process physiology data associated with the plurality ofsensor types respectively using a plurality of modality specificinstructions; and generate a graphical representation based on thephysiology data. The first display is operable to display the graphicalrepresentation based on the physiology data.

In some embodiment, the intraluminal medical system of the presentdisclosure further includes the intraluminal device. In someembodiments, the plurality of sensor types includes a plurality ofintravascular ultrasound (IVUS) sensor types. In some implementations,the plurality of IVUS sensor types includes a plurality of transducercenter frequencies. In some instances, the plurality of sensor typescomprises an imaging sensor, an ultrasound transducer, an ultrasoundtransducer array, an optical sensor, a pressure sensor, and a flowsensor. In some embodiments, the intraluminal medical system of thepresent disclosure further includes a signal conditioning circuitdisposed within the housing. The signal conditioning circuit can becoupled to the intraluminal device and operate to condition thephysiology data from the intraluminal device.

In some embodiments, the intraluminal medical system of the presentdisclosure further includes an analog to digital converter (ADC)disposed within the housing. The ADC can be coupled to the signalconditioning circuit and operate to digitize the physiology data fromthe signal conditioning circuit. In some implementations, the controllercore is further operable to configure the signal conditioning circuitbased on a modality of the identified sensor. In some implementations,the controller core is further operable to configure the computing corebased on the modality of the identified sensor. In some instances, thecontroller core is operable to identify the sensor of the intraluminaldevice by sending a sensing signal to the intraluminal device andmeasuring an impedance of the intraluminal device in response to thesensing signal. In some embodiments, the intraluminal medical system ofthe present disclosure further includes a communication module disposedwithin the housing. The communication module is operable to transmit thegraphical representation of the physiology data to a second displayapart from the medical system.

In another embodiment, a method of obtaining physiology data isprovided. The method includes controlling, using a controller coredisposed within a housing of a handheld interface device, a sensor of anintraluminal device positioned within a body lumen of a patient toobtain physiology data associated with the body lumen, wherein thecontroller core is configured to control a plurality of sensor typesrespectively associated with a plurality of intraluminal devices;identifying the sensor of the intraluminal device, using the controllercore of the handheld interface device; processing, using a computingcore disposed within the housing of the handheld interface device, thephysiology data using instructions associated with the identifiedsensor, wherein the computing core is further operable to processphysiology data associated with the plurality of sensor typesrespectively using a plurality of modality specific instructions;generating, using the computing core, a graphical representation basedon the obtained physiology data; and displaying, using a first displayintegrated in the housing of the handheld interface device, thegraphical representation of the physiology data.

In some embodiments, the method of the present disclosure furtherincludes configuring, using the controller core, the computing corebased on a modality of the identified sensor. In some embodiments, themethod of the present disclosure further includes conditioning thephysiology data, using a signal conditioning circuit disposed within thehousing. In some implementations, the method of the present disclosurefurther includes configuring, using the controller core, the signalconditioning circuit based on a modality of the identified sensor. Insome embodiments, the method of the present disclosure further includesdigitizing the physiology data, using an analog to digital converter(ADC) disposed within the housing. In some embodiments, the method ofthe present disclosure further includes configuring, using thecontroller core, the ADC based on a modality of the identified sensor.In some implementations, the method of the present disclosure furtherincludes transmitting, using a communication module disposed within thehousing, the graphical representation of the physiology data to a seconddisplay apart from the handheld interface device. In some embodiments,the plurality of sensor types comprises a plurality of IVUS sensortypes. In some instances, the plurality of IVUS sensor types comprises aplurality of transducer center frequencies.

Additional aspects, features, and advantages of the present disclosurewill become apparent from the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present disclosure will be describedwith reference to the accompanying drawings, of which:

FIG. 1 is a diagrammatic schematic view of a prior-art intraluminalmedical system.

FIG. 2 is a functional block diagram of a medical system, according toaspects of the present disclosure.

FIG. 3 is a diagrammatic schematic view of a medical system, accordingto aspects of the present disclosure.

FIG. 4 is a functional block diagram of a software framework executingon the medical system, according to aspects of the present disclosure.

DETAILED DESCRIPTION

For the purposes of promoting an understanding of the principles of thepresent disclosure, reference will now be made to the embodimentsillustrated in the drawings, and specific language will be used todescribe the same. It is nevertheless understood that no limitation tothe scope of the disclosure is intended. Any alterations and furthermodifications to the described devices, systems, and methods, and anyfurther application of the principles of the present disclosure arefully contemplated and included within the present disclosure as wouldnormally occur to one skilled in the art to which the disclosurerelates. In particular, it is fully contemplated that the features,components, and/or steps described with respect to one embodiment may becombined with the features, components, and/or steps described withrespect to other embodiments of the present disclosure. For the sake ofbrevity, however, the numerous iterations of these combinations will notbe described separately.

FIG. 1 is a diagrammatic schematic view of a prior-art intraluminalmedical system 100. The prior-art intraluminal medical system 100includes an intraluminal device 101, a patient interface module (PIM)102 and a console 103. The intraluminal device 101 is connected to thePIM 102, which is connected to the console 103. The console 103 isusually bulky and may include wheels such that it can be wheeled around.For that reason, the prior-art intraluminal medical system 100 lacksmobility and takes up space in catheter labs.

Referring now to FIG. 2, shown therein is a functional block diagram ofa medical system 200, according to aspects of the present disclosure.The medical system 200 includes an intraluminal device 202 and ahandheld interface device 220. The handheld interface device 220 isapproximately of the size of a tablet or a laptop and all of itsphysical components, such as circuitry, a display, and a user inputdevice are disposed within or integrated with a housing 201. Thephysical components will be described in more detail in conjunction withFIG. 3 below. A user can hold the handheld interface device 220 with onehand. Alternative, in some embodiments, the handheld interface device220 may include a stand that allows the handheld interface device 220 tobe positioned on a horizontal surface or secured to a hospital bed rail.The intraluminal device 202 is configured to be inserted into a bodylumen of a patient to obtain physiology data of the body lumen. In someembodiments, the physiology data obtained by the intraluminal device 202include analog data and are too large to be transmitted via a digitalcable. In those embodiments, the intraluminal device 202 is connected tothe handheld interface device 220 via an analog cable or via a wirelessconnection. In the former case, the housing 201 includes at least aconnection port for connecting the intraluminal device 202. In thelatter case, both the handheld interface device 220 and the intraluminaldevice 202 have a wireless signal transceiver in compliance with theIEEE 802.11a, 802.11b/g/n and 802.11ac standards. In some embodiments,the wireless signal transceiver can utilize other wireless protocols,such Wireless Local Area Network (WLAN), Wireless Personal Area Network(WPAN), IrDA, Bluetooth, Zigbee, UWB, etc.

In some embodiments, the medical system 200 and/or the handheldinterface device 220 can include features similar to those described inU.S. Patent Application No. 62/574,455, titled “DIGITAL ROTATIONALPATIENT INTERFACE MODULE,” filed Oct. 19, 2017, U.S. Patent ApplicationNo. 62/574,655, titled “WIRELESS DIGITAL PATIENT INTERFACE MODULE USINGWIRELESS CHARGING,” filed Oct. 19, 2017, U.S. Patent Application No.62/574,687, titled “INTRALUMINAL DEVICE REUSE PREVENTION WITH PATIENTINTERFACE MODULE AND ASSOCIATED DEVICES, SYSTEMS, AND METHODS,” filedOct. 20, 2017 and U.S. Patent Application No. 62/574,835, titled“INTRALUMINAL MEDICAL SYSTEM WITH OVERLOADED CONNECTORS,” filed Oct. 20,2017, each of which is incorporated by reference in its entirety.

With the handheld interface device 220, the medical system 200 of thepresent disclosure is smaller, lightweight, portable, takes less space,and costs much less for installation. In addition, the medical system200 includes fewer discrete components and is easy to install and setup. As a result, the medical system 200 of the present disclosureadvantageously makes the catheter diagnosis tools more readily availableto the clinician and more likely to be used in time-sensitivesituations.

Referring now to FIG. 3, shown there is a diagrammatic schematic view ofthe medical system 200. The handheld interface device 220 includes ahousing 201. In some embodiments represented by FIG. 3, a signalconditioning circuit 204, an analog to digital converter (ADC) 206, acontroller core 208, a computing core 212, an input device 222, and adisplay 214 are coupled to the housing 201. The housing can be anysuitable shape including a volume (e.g., a height, a width, a depth, aradius, etc.) in which the signal conditioning circuit 204, the analogto digital converter (ADC) 206, the controller core 208, the computingcore 212, the input device 222, and the display 214 are positioned, forexample. In some embodiments, the display 214 can form a surface of thehousing 201. The intraluminal device can include a flexible elongatemember sized and shaped, structurally arranged, and/or otherwiseconfigured to be positioned within a body lumen of a patient. Forexample, the intraluminal device can be an intravascular deviceconfigured to be positioned within a blood vessel of a patient, in someembodiments. The intraluminal device can include a flexible elongatemember having a proximal portion and a distal portion. A sensorconfigured to obtain physiology data (e.g., imaging, pressure, flow,temperature, etc.) associated with the body lumen is disposed at thedistal portion of the intraluminal device. In some embodiments, theintraluminal device 202 can be an intravascular ultrasound (IVUS)device, a near infrared (NIR) imaging device, an optical coherencetomography (OCT) device, an intravascular photoacoustic (IVPA) imagingdevice, a transesophageal echocardiography (TEE) device, an intracardiacechocardiography (ICE) device, or a flow rate catheter. For example, theintraluminal device 202 can be a phased array IVUS device, including anarray of transducer circumferentially and/or annularly arranged around alongitudinal axis. In some embodiments, the intraluminal device 202 canbe a rotational IVUS device, including a rotating drive cable thatrotates an IVUS transducer. The intraluminal device 202 includes one ormore sensors. For example, when the intraluminal device 202 is a NIRimaging device or an OCT device, the sensors of the intraluminal device202 include imaging sensors, such as an optical sensor, or an infraredsensor. When the intraluminal device 202 is a flow rate catheter, thesensors are pressure sensors and flow rate sensors. In some embodiments,when the intraluminal device is an IVUS device, the sensors areultrasound transducers, which can be a piezoelectric micromachinedultrasound transducer (PMUT), capacitive micromachined ultrasonictransducer (CMUT), single crystal, lead zirconate titanate (PZT), PZTcomposite, other suitable transducer type, combinations thereof, and/orarrays thereof. In some embodiments, when the intraluminal device 202 isan IVUS device, the intraluminal device 202 can include additionalsensors, including a pressure sensor, a flow sensor, a temperaturesensor, an optical fiber, a reflector, a mirror, a prism, and/orcombinations thereof. In those embodiments, the additional sensors canbe activated in the intraluminal device 202 in lieu of or in addition tothe ultrasound transducers.

When in use, the intraluminal device 202 is connected to the handheldinterface device 220. In some embodiments, the intraluminal device 202is connected to the handheld interface device 220 via an analog signalcable. In some other embodiments, the intraluminal device 202 isconnected to the handheld interface device 220 wirelessly. Thecontroller core 208 can identify the modality or sensor type of theintraluminal device 202 and operating parameters of the intraluminaldevice, such as a center frequency of ultrasound transducers when theintraluminal device 202 is an IVUS device. Taking diagnostic IVUSimaging for example, the center frequency of the ultrasoundtransducer(s) can be between 2 MHz and 70 MHz, for example, includingvalues such as 10 MHz, 20 MHz, 40 MHz, 45 MHz, 60 MHz, and/or othersuitable values both larger and smaller. For example, lower frequencies(e.g., 10 MHz, 20 MHz) can advantageously penetrate further into thetissue around the body lumen. Higher frequencies (e.g., 45 MHz, 60 MHz)can be better suited to generate more detailed ultrasound images of thebody lumen and/or fluids within the body lumen. In some embodiments, thefrequency of the ultrasound transducer is tunable. For imaging, in someinstances, the ultrasound transducer can be tuned to receive wavelengthsassociated with the center frequency and/or one or more harmonics of thecenter frequency. In some instances, the frequency of the emittedultrasonic energy can be modified by the voltage of the appliedelectrical signal and/or the application of a biasing voltage to theultrasound transducers. In some embodiments, the controller core 208supplies the electrical signal and the biasing voltage to the ultrasoundtransducer. In some implementations, the handheld interface device 220is configured to control a plurality of sensors associated with aplurality of intraluminal devices. The ability for the controller core208 to identify the modality or sensor type of the intraluminal device202 allows the medical system 200 to operate in different intraluminalmodality. In some instances, ultrasound transducers with differentcenter frequencies can be considered different sensor types. In someother instances, tunable ultrasound transducers can be considered adifferent type of sensors from fixed frequency ultrasound transducers.

In some embodiments, the handheld interface device 220 includes a“sleeping mode,” in which the power consumption of the handheldinterface device 220 is maintained at a low level and the controllercore 208 does not transmit any control signals to the intraluminaldevice 202. In embodiments where the intraluminal device 202 isconnected to the handheld interface device 220 by an analog signalcable, the controller core 208 can constantly or periodically output asensing signal via the connection port. When the intraluminal device 202is not connected to the handheld interface device, the sensing signalsees no impedance and the handheld interface device 220 stays in the“sleeping mode.” However, when an intraluminal device 202 is connectedto the handheld interface device 220, the sensing signal sees animpedance and the controller core 208 can detect the impedance and wakeup from the “sleeping mode.” In some embodiments, the controller core208 can identify the modality/type and operating parameters of theintraluminal device 202 by comparing the impedance seen by the sensingsignal to characteristic impedance values of a plurality of intraluminaldevices 202 that are compatible with the handheld interface devices 220.The intraluminal device 202 can include a memory, such as anelectrically erasable programmable read-only memory (EEPROM), in someembodiments. The EEPROM can store the modality/type and operatingparameters of the intraluminal device 202 or encoded data representingthe same. The controller core 208 can identify the modality/sensor typeand operating parameters of the intraluminal device 202 by reading theEEPROM in such embodiments. Because the handheld interface device canidentify the modality and sensor type of the intraluminal device 202,the handheld interface device 220 is configured to be operable with aplurality of intraluminal devices 220 (e.g., having different sensortypes). In embodiments where the intraluminal device 202 is connected tothe handheld interface device 220 wirelessly, the controller core 208 ofthe handheld interface device 220 can constantly or periodicallybroadcast a sensing signal or a beacon wirelessly. The intraluminaldevice 202 within a range of the sensing signal or beacon can respondthe sensing signal or beacon by a linking signal. Once the handheldinterface device 220 receives a linking signal, the controller core 208can cause the computing core 212 to output a dialogue box to the display214, asking a user for permission or confirmation to initiate connectionwith the intraluminal device 202. When the user permits or confirmsconnection with the intraluminal device 202, the handheld interfacedevice 220 can wake up from the “sleeping mode” and connect to theintraluminal device 202.

After the controller core 208 identifies the modality/sensor type of theintraluminal device 202, the controller core 208 would configure thesignal conditioning circuit 204, the ADC 206 and the computing core 212based on the modality/sensor type and operating parameters of theintraluminal device 202. In some embodiments, the controller core 208configures the signal conditioning circuit 204 by selecting acombination of amplifiers and band-pass filters suitable for theidentified modality or sensor type of the intraluminal device 202. Insome implementations, the controller core 208 configures the ADC 206 bychanging parameters associated with the ADC 206. In some instances, theparameters may include a reference voltage fed to the ADC 206. In stillsome embodiments, the controller core 208 configures the computing core212 by changing the set of instructions or algorithms to process thephysiology data and to generate graphical representation of thephysiology data. In some implementations, each modality or each sensortype of the intraluminal device 202 corresponds to a modality-specificor sensor-specific instructions or algorithms. The intraluminal device202 is inserted into a body lumen of a patient. In response to controlsignal from the controller core 208, the sensors of the intraluminaldevice 202 obtain physiology data of the body lumen of the patient. Theintraluminal device 202 then sends the obtained physiology data to thesignal conditioning circuit 204. In some embodiments, the signalconditioning circuit 204 includes amplifiers, band-pass filters andother signal enhancing and/or noise reduction circuitry. In someinstances, the medical system 200 can include structures disclosed inU.S. Patent Application No. 62/574,455, titled “DIGITAL ROTATIONALPATIENT INTERFACE MODULE,” filed Oct. 17, 2017, or U.S. PatentApplication No. 62/574,655, titled “WIRELESS DIGITAL PATIENT INTERFACEMODULE USING WIRELESS CHARGING,” filed Oct. 17, 2017, each of which isincorporated by reference in its entirety. The signal conditioningcircuit 204 conditions the obtained physiology data and sends theconditioned physiology data to the ADC 206. The ADC 206 converts theconditioned physiology data from analog forms into digital forms. Insome instances, the analog to digital conversion performed by the ADC206 may be referred to herein as digitizing or digitization from time totime.

The digitized physiology data is then sent to the controller core 208.The controller core 208 can then encode the digitized physiology datafor low-voltage different signaling (LVDS) transmission to the computingcore 212. The LVDS transmission is not without its limit. In someinstances, it can support physiology data transmission up to around 3Gbit/s. In some embodiments illustrated in FIG. 3, the handheldinterface device 220 further includes a communication interface 210. Insome embodiments, the communication interface 210 is a physical layerdevice that can modulate digitized physiology data for transmission ratebeyond 3 Gbit/s. In those embodiments, instead of sending the digitizedphysiology data to the computing core 212 directly via LVDS, thecontroller core 208 first sends the digitized physiology data to thecommunication interface 210. The communication interface 210 thenmodulates the digitized physiology data based on a communicationprotocol and transmits the modulated physiology data to the computingcore 212. In some instances, the communication protocol includes theUSB3.0 protocol and the 10 Gb Ethernet protocol. In implementationswhere the physiology data transmission rate is below 3 Gbit/s, thecommunication interface 210 is optional. However, in implementationswhere the physiology data transmission rate is beyond 3 Gbit/s, thecommunication interface 210 can improve the transmission rate andprovides more satisfactory user experience.

In embodiments where the physiology data is modulated beforetransmission to the computing core 212, the computing core 212demodulates the modulated physiology data before it processes thephysiology data, generates a graphical representation of the physiologydata, and outputs the graphical representation to the display 214 fordisplay. In other embodiments where the digitized physiology data istransmitted to the computing core 212 by LVDS, the computing core 212does not need to demodulate the received physiology data beforeprocessing the same. In some embodiments, the handheld interface device220 may include an input device 222. In some instances, the input device222 is a touch sensor integrated with the display 214. In someembodiments, the computing core 212 and the controller core 208 may beseparate cores or separate groups of cores of one processor 211, such asa central processing unit (CPU). In some embodiments, the computing core212 and/or the controller core 208 can be a field-programmable gatearray (FPGA). In embodiments where the controller core 208 and thecomputing core 212 are parts of one processor, the handheld interfacedevice 220 does not have the communication interface 210. In someembodiments, the handheld interface device 220 may further include acommunication module 216, which can broadcast the physicalrepresentation of the physiology data to one or more remote display(s)218. Different from display 214, which is integrated with the housing201, the display 218 is apart from the handheld interface device 220. Insome implementations, the display 218 is larger than display 214 and isconfigured to display the graphical representation in higher resolutionor in more detail. In some embodiments, the handheld interface device220 can communicate with a remote server or database by use of thecommunication module 216. For example, in response to a user input, thecomputing core 212 can cause the communication module 216 to initiate aconnection with a remote server or a database so as to retrievephysiology data or imaging data of the patient.

The body lumen, as used herein, can be a vessel, such as a blood vessel.In various embodiments, the body lumen is an artery or a vein of apatient's vascular system, including cardiac vasculature, peripheralvasculature, neural vasculature, renal vasculature, and/or any othersuitable anatomy/lumen inside the body. The body lumen can be tortuousin some instances. For example, the intraluminal device 202 may be usedto examine any number of anatomical locations and tissue types,including without limitation, organs including the liver, heart,kidneys, gall bladder, pancreas, lungs, esophagus; ducts; intestines;nervous system structures including the brain, dural sac, spinal cordand peripheral nerves; the urinary tract; as well as valves within theblood, chambers or other parts of the heart, and/or other systems of thebody. In addition to natural structures, the intraluminal device 202 maybe used to examine man-made structures such as, but without limitation,heart valves, stents, shunts, filters and other devices.

FIG. 4 is a functional block diagram of a software framework 300executing on the medical system 200, according to aspects of the presentdisclosure. In some embodiments, the software framework 300 executes onthe computing core 212. The software framework 300 includes a pluralityof software layers that manage various aspects of the medical system 200shown in FIGS. 2 and 3. For instance, an operating platform 302undergirds the software framework 300 and provides the corefunctionality of the medical system 200. For instance, the operatingplatform 302 may manage power consumption and distribution of themedical system 200 and may also manage network connectivity, forexample, connection via the communication module 216 to the display 218or a remote server where the physiology data of patients are stored.Further, the software framework 300 may include a graphics engine 304operable to process physiology data and generate graphic representationof the physiology data. Additionally, the software framework 300includes a co-registration engine 306 operable to align, co-register orfuse physiology data obtained using different modality of intraluminaldevice 202. For example, flow rate or pressure data of a body lumen of apatient can be co-registered with IVUS imaging data obtained from thesame body lumen of the patient. The software framework 300 also includesa data management engine 308 operable to download from a server andupload to a server physiology data and patient information of a patient.Further, the data management engine 308 is operable to assign apatient-specific identifier to the graphical representation of thephysiology data of the patient such that the graphical representation ofthe patient's physiology data can be stored and filed according to thepatient's identification. In some embodiments, the patient-specificidentifier (also referred to as the patient identifier) can be asystem-assigned patient number or a number shown on the patient'sgovernment-issued identification card.

The software framework 300 includes an application layer 310 in whichapplications associated with particular sensor types (e.g., differentcenter frequencies from IVUS transducer and/or other intraluminalmodalities, such as pressure, flow, OCT, etc.) may execute. Theapplications in the application layer 310 may be operable to generategraphical representations of the physiology data obtained from the bodylumen of the patient. In embodiments shown in FIG. 4, the applicationlayer 310 may include a first intraluminal modality application 310-1, asecond intraluminal modality application 310-2, and the n^(th)intraluminal modality application 310-N. Each of the applications isassociated with a graphic user interface (GUI) geared towards displayingthe graphical representation and relevant data. In some embodiments, atthe GUI of each of the application, a user can check availablephysiology data for possible cross-modal co-registration. The differentmodalities of physiology data can be those obtained by a differentintraluminal device or those stored in a remote server/database underthe patient's identifier. For example, the first intraluminal modalityapplication 310-1 can be specifically associated with an IVUSintraluminal device 202 with ultrasound transducers as its sensors, andthe second intraluminal modality application 310-2 can be specificallyassociated with an OCT intraluminal device 202 with optical sensors.After the patient's body lumen is examined by use of the IVUS and OCTintraluminal devices, at either GUI of the first and second intraluminalmodality applications, a user can select to fuse the graphicalrepresentations based on the IVUS and OCT physiology data. In someinstances where the patient is subject to electrocardiogram (ECG)monitoring or three-dimensional (3D) angiography and the ECG andangiography data are stored in a server/database accessible by theco-registration engine 306, the application may present the user withoptions to co-register the IVUS or OCT data with the ECG or angiographicdata.

Persons skilled in the art will recognize that the apparatus, systems,and methods described above can be modified in various ways.Accordingly, persons of ordinary skill in the art will appreciate thatthe embodiments encompassed by the present disclosure are not limited tothe particular exemplary embodiments described above. In that regard,although illustrative embodiments have been shown and described, a widerange of modification, change, and substitution is contemplated in theforegoing disclosure. It is understood that such variations may be madeto the foregoing without departing from the scope of the presentdisclosure. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the presentdisclosure.

What is claimed is:
 1. An intraluminal medical system, comprising: ahandheld interface device configured for communication with a pluralityof different intraluminal devices configured to be positioned within abody lumen of a patient, wherein the plurality of different intraluminaldevices respectively comprises a plurality of sensors corresponding to aplurality of sensor types and configured to obtain intraluminal data,the handheld interface device comprising: a housing sized and shaped forhandheld use; an individual processor disposed within the housing,wherein the individual processor comprises a controller core and acomputing core; an analog to digital converter (ADC) disposed within thehousing and configured to digitize the intraluminal data, wherein theADC is in direct communication with the controller core; and a firstdisplay integrated in the housing, wherein the controller core isoperable to: identify a sensor of an intraluminal device incommunication with the handheld interface device as one of the pluralityof sensor types; and configure the computing core and the ADC based onthe identified sensor type; and wherein the computing core is configuredto execute a plurality of sensor-specific instructions associated withthe plurality of sensor types, wherein, to configure the computing core,the controller core is configured to change sensor-specific instructionsexecuted by the computing core for each identified sensor type such thatthe computing core is operable to: process the intraluminal dataobtained by the sensor using the sensor-specific instructions for theidentified sensor type; and generate a graphical representation based onthe intraluminal data using the sensor-specific instructions for theidentified sensor type, wherein, to configure the ADC, the controllercore is configured to select, based on the identified sensor type, asensor-specific reference voltage provided to the ADC to digitize theintraluminal data, and wherein the first display is operable to displaythe graphical representation based on the intraluminal data.
 2. Thesystem of claim 1, wherein the plurality of sensor types comprises aplurality of IVUS sensor types.
 3. The system of claim 2, wherein theplurality of IVUS sensor types comprises a plurality of transducercenter frequencies.
 4. The system of claim 1, wherein the plurality ofsensor types is at least two of an imaging sensor, an ultrasoundtransducer, an ultrasound transducer array, an optical sensor, apressure sensor, or a flow sensor.
 5. The system of claim 1, furtheringcomprising: a signal conditioning circuit disposed within the housing,the signal conditioning circuit coupled to the intraluminal device andoperable to condition the obtained intraluminal data from theintraluminal device.
 6. The system of claim 5, wherein the ADC iscoupled to the signal conditioning circuit and operable to digitize theconditioned intraluminal data from the signal conditioning circuit. 7.The system of claim 5, wherein the controller core is operable toidentify the sensor of the intraluminal device by sending a sensingsignal to the intraluminal device and measuring an impedance of theintraluminal device in response to the sensing signal.
 8. The system ofclaim 1, further comprising: a communication module disposed within thehousing, the communication module operable to transmit the graphicalrepresentation based on the obtained intraluminal data to a seconddisplay apart from the medical system.
 9. The system of claim 1, whereinthe computing core is further configured to: co-register theintraluminal data obtained from at least two sensors of the plurality ofsensors; and generate a graphical representation based on theco-registered intraluminal data, and wherein the first display isoperable to display the graphical representation based on theco-registered intraluminal data.
 10. The system of claim 1: wherein thehousing sized and shaped for handheld use is a single housing, whereinthe controller core and computing core are disposed within the singlehousing, and wherein the first display is integrated in the singlehousing.
 11. The system of claim 1, further comprising one or more ofthe plurality of different intraluminal devices.
 12. The system of claim1, wherein the plurality of sensor types comprise a plurality ofintraluminal modalities, and wherein the plurality of sensor-specificinstructions comprises a plurality of modality-specific instructions.13. The system of claim 5, wherein the controller core is configured toselect, based on the identified sensor type, a sensor-specificcombination of amplifiers and band-pass filters.
 14. The system of claim1, wherein the controller core is configured to control the plurality ofsensor types using a plurality of sensor-specific control signals suchthat the controller core controls the sensor of the intraluminal deviceto obtain the intraluminal data based on the identified sensor type. 15.The system of claim 1, wherein the individual processor comprises atleast one of a central processing unit (CPU) or a field-programmablegate array (FPGA).
 16. The system of claim 1, wherein the controllercore configures the ADC by changing parameters associated with the ADC,wherein the parameters include the sensor-specific reference voltageprovided to the ADC.
 17. The system of claim 5, wherein controller coreis operable to configure the signal conditioning circuit based on theidentified sensor type, wherein the controller core configures thesignal conditioning circuit by selecting a combination of amplifiers andband-pass filters suitable for the identified sensor type.